@varungup90 can you squash the commits to pass DCO?

Why not directly generate it using cryptographic randomness? That would be more compliant with the standards.

Why not directly generate it using cryptographic randomness? That would be more compliant with the standards.

It requires same seed to generate same hash value for prompt's prefix.

For security-focused scenarios in Go, it might be better to use the crypto/rand package instead of math/rand. You could try something like this:

import (
    "crypto/rand"
    "encoding/binary"
)

func generateSecureSeed() (uint64, error) {
    var seed uint64
    if err := binary.Read(rand.Reader, binary.BigEndian, &seed); err != nil {
        return 0, err
    }
    return seed, nil
}

This complies with the random number generation specifications. In fact, rand.New(rand.NewSource(time.Now().Unix())) should never be used under any circumstances.

@kexinoh Sounds good, you can send a PR to add generateSecureSeed method in pkg/util.